Overview of State SyncUp

This topic describes the overview of State Syncup.

An overview about the members involved in a ring is as follows:

Communication between the members of the default ring

 

• The OpenText Process Suite Platform (<instance name>)s form the ring.
• The Master SyncUp (the SyncUp instance within the monitor) receives and sends messages and acts as a member of the ring.
• The communication between the members happen using TCP.

Role of default ring

 

• LDAP cache invalidation and Service Container state like start, stop or in 'problem' is communicated using the ring.
• Process Platform provides a smart routing mechanism based on SyncUp. Using this mechanism, a client can identify the Service Containers that are down, and accordingly, route messages to another Service Container. This information is available locally with the client and such a routing decision is taken instantly.

Role of the Master SyncUp

 

• The master SyncUp instance in the monitor communicates with the SyncUp in the Service Containers. The SyncUp in the Service Container is known as the Local SyncUp. The communication between the monitor (master SyncUp) and Service Container (local SyncUp) occurs through the TCP protocol and is one-to-one. The local SyncUp instances communicate with the master SyncUp on the same machine.
• The master SyncUp at the monitor updates the state registry with the content for individual Service Container on that machine, using the local SyncUp instance.
• Broadcast messages are sent to the broadcast module and state registry messages are sent to all associated state registries, at master SyncUp and local SyncUp, over TCP/IP.
• Each OpenText Process Suite Platform (<instance name>) may again have multiple remote clients that communicate from another machine. These constitute the Remote SyncUp instances. The communication between the monitor and remote clients occurs through the TCP protocol and is one-to-one.
• Remote SyncUp follows both Broadcasting and State Registry communication types. However, it cannot modify the content of State Registry.
• State Registry messages (Stateful messages) - These are dispatched to the local state registry and to state registries attached to it, through the local and remote syncup instances.
• Broadcast messages (Stateless messages) - These messages are published to people who subscribe to it.